Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1587

reference: 283-tree-1
name: 1587
tree-preservation-order: undefined
283-tpo-1
uprn
address-text
point: POINT (-1.041001 50.897615)
geometry: MULTIPOLYGON (((-1.040959 50.897610,-1.040961 50.897618,-1.040967 50.897626,-1.040976 50.897632,-1.040988 50.897636,-1.041001 50.897637,-1.041014 50.897636,-1.041026 50.897632,-1.041036 50.897626,-1.041042 50.897619,-1.041044 50.897611,-1.041042 50.897602,-1.041036 50.897595,-1.041027 50.897589,-1.041015 50.897585,-1.041002 50.897583,-1.040977 50.897588,-1.040967 50.897594,-1.040961 50.897602,-1.040959 50.897610)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL